Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@quenty/permissionprovider

Package Overview
Dependencies
Maintainers
0
Versions
263
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@quenty/permissionprovider

Permission provider for Roblox, including authenticating against group membership

  • 14.16.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
426
increased by102.86%
Maintainers
0
Weekly downloads
 
Created
Source

Permission Provider

Documentation status Discord Build and release status

Utility permission provider system for Roblox

Installation

npm install @quenty/permissionprovider --save

Permission designs

This permissions system originally supported the following scenarios:

  1. Any game has a default admin scheme based upon who can edit the game
  2. Can override this configuration (although in practice this isn't required)

New permission features

The following features need to be added.

  1. Extensibility: Ability to add / modify default behavior via chain-of-command.
  2. Data-store based: Ability to modify based upon a datastore using admin commands, et cetera.

Role based permission support

Permissions right now are global per a game. We need configurable, sharable, editable non-global permissions. This will require the following support.

  1. Permission serialization - Can save permissions to the datastore
  2. Permission provisioning per a state

The goal is to use this package as a backend for permissioning such that this package can understand and provide permissions that work out of the default. Permissioning model should act like Discord roles, where tagging is separated out from the actual permissions associated with a role.

This will require a roles package separate from this permission system. This can probably be done in separate packages roles and role-permissions which may not be open source available. Then, UI can be done in role-permission-ui and be generalized and reused. This will also likely not be open source

We may leverage a role-provisioning system to handle permissions. We should build this role system and then assign permissions against the roles at this permission provider layer.

Keywords

FAQs

Package last updated on 03 Dec 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc